BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / gt_power / trac153.zip / TRACBETA.DOC < prev next >

Wrap

Text File | 1990-10-27 | 57KB | 1,202 lines

Tracker v1.53 - October 27, 1990 - Logon utility for GT15.XX ------------------------------------------------------------------------------ v1.53 - PUBLIC RELEASE ------------------------------------------------------------------------------ v1.53 notes ----------- * Fixed bug that would tell caller 1 he was number 0. * Support for GT 16 message files added. If you are using GT 15 or 16, you must run TRACKER CONFIG and set the (V)ersion of GT you are using to either 15 or 16! It is very important for everyone to do this so that the code will work properly! * Fixed problem of undeleted messily-named users appearing on an INIT * Other miscellaneous bugs have been caught and smashed. Tracker v1.52 - June 16, 1990 - Logon utility for GT15.XX ------------------------------------------------------------------------------ v1.52 - PUBLIC RELEASE ------------------------------------------------------------------------------ v1.52 notes ----------- I knew this would happen.. Well, we've got all of the obviously foul bugs out now (I hope). Bug was fixed that caused a "String space corrupt" when scanning. I removed the entire function and did less directory checking, so don't be alarmed if it says something like "Path not found" or "Directory does not exist".. everything will work out, although I can't stress to you enough that the temporary path you've set up in the CONFIG should NOT BE ANY EXISTANT DIRECTORY!! I will not be able to be contacted except through the BBS until June 30, at which time I will be around for a day or two, then not again until July 13, then I'll be here for a week, then not until August 1, 1990. Please leave messages concerning Tracker on my BBS or in netmail to 070/002 if possible. Thanks, Cory Tracker v1.51 - June 16, 1990 - Logon utility for GT15.XX ------------------------------------------------------------------------------ v1.51 - PUBLIC RELEASE ------------------------------------------------------------------------------ v1.51 notes ----------- Whoops! I screwed up a few things on the command line like getting the comport and the exemptions right. It turns out that v1.50 could have only been run on the default COM1:. This is now fixed and PORT: is no longer a valid command line parameter. Your comport is found from the GT.CNF file. The EXEMPT: parameter has also been taken off of the command line and placed into the configuration menu. Sorry about that! Tracker v1.50 - June 15, 1990 - Logon utility for GT15.XX ------------------------------------------------------------------------------ v1.50 - PUBLIC RELEASE ------------------------------------------------------------------------------ v1.50 notes ----------- A staggering 4 month delay and it's still beta! This program may hold a record for being in beta test the longest. Since August 19, 1989, Tracker has undergone many different changes and improvements--none of which could have been acheived without the valiant efforts of the beta testers. To name a few: 079/003 Bill Wahlstrom 029/008 Ed Bragg 069/004 James Craig 032/001 Perry Alexander 064/003 Rob Roesch 081/003 Bob Carson 075/001 Douglas Pippel 006/000 Keith Coyne 004/005 April Strong 079/000 Bryan Pike 050/022 Andrew Leeder But there are many more, and if I've missed your name, I'm sorry. * Please note: If you were running the latest version of Tracker (v1.39E), there is a remote possiblity that your configuration file will not work, or that some functions will not be valid. Therefore, I recommend you run TRACKER CONFIG and look around, then (Q)uit and save. If that still doesn't work, be sure you have all your info written down, delete TRACKER.CNF, and run TRACKER CONFIG again. Now, the new features. Standard documentation and new user instructions can be found in the TRACKER.DOC file. * removed all /'s from the command line parameters. You need not change your batch files, though, because either /INIT or INIT will work. The same applies to all other parameters. * Added the @N@ code for "calls today" by user. For example: "John, you've called @N@ times today" or "John, this is call #@N@". * More organized information at bottom of screen. Kinda looks like PCBoard. * Removed beta CRC activation. There is no difference in feature availability between the registered and unregistered versions, however. * Lots of code tweaking! ------------------------------------------------------------------------------ Tracker v1.39ßE - February 14, 1990 - Logon utility for GT15.XX ------------------------------------------------------------------------------ v1.39 BETA E - NOT AUTHORIZED FOR RELEASE TO THE GENERAL PUBLIC ------------------------------------------------------------------------------ v1.39ßE notes ------------- New feature via /CONFIG is the 'Use Mail Scanning?' option. Answer Y if you wish to use the mail scanning option. You need to change nothing if you continue to use mail scan. If you STOP mail scanning, you need to delete the TRACKER.CTL and TRACKER.NDX files. You must still run Tracker in logon and TRACKER /END in logoff. (also, be sure to answer N in /CONFIG to the mailscan question.) Also, run TRACKER to see what is output. The output is a little different if you don't use the mail scan feature (ie: you lose the 'MAIL WAITING' line. I'm still trying to track down an error in computing logoff time when the hour is between midnight and 1. I hope to correct it soon. Cory ------------------------------------------------------------------------------ v1.39 BETA - NOT AUTHORIZED FOR RELEASE TO THE GENERAL PUBLIC ------------------------------------------------------------------------------ v1.39 notes: (time span from 1.38 - 17 days) NO CRC CHANGE! ----------- This is basically a maintanence release. You need to run TRACKER /CONFIG and recheck your parameters. You will note that a few things have been added/changed: An alternate GTMDIR.BBS-type file is now available for you to configure. All you need to do is specify an alternate in the correct field (choice D in /CONFIG) of a file in the GTMDIR.BBS format. This will enable all of you to restrict your messages to be scanned. * The time left bug has been conquered & corrected in 1.39 * More options have been added to the configuration menu and the menu colors themselves have been adjusted to fit your colors. GATEWAY or any other redirection must NOT be active during Tracker's operation due to the fact that true ANSI screen writes are made for parts of the local screen and will echo out double if redirected!! The SCAN function has not been touched in this release, but I hope to be recoding in C for 1.40 within the month. I hope that the configurable GTMDIR file will ease the pain for a while... Cory ---- v1.38 notes: (time span from 1.37 - 2 days) NO CRC CHANGE! ----------- Includes some quick fixes such as updating PTMDIR.BBS in the correct fashion, and correcting output of color codes in the correct manner. The code to switch to dim colors is ^[[2;xxm or ^[[0;xxm. Apparently, my routines to toss the ANSI to the screen did not like the ^[[2 codes, which I was using, so I switched to the ^[[0 set which adhere to the ANSI standard as printed in the DOS 2.00 manual. You could have patched that one with a sector editor with no problem, but basically, it required a total re-release.. Thanks for staying with me. The /NOxxxx commands were fixed as well and should be operating properly. The ACCEPT.TRC file can be either be used or not to accept a certain baud rate that you have locked out according to user name. Memory information has also been included in 1.38 at the bottom of most screens to help you decide if you need to free up some memory. Also, I meant to mention that, in order to be safe, be sure you have at least 200k free in when running in your GTLOGON.BAT and GTLOGOFF.BAT. Tracker can be quite a hog esp with large user bases. I've even experienced an out-of-memory error with 519k free while scanning, so keep an eye out and let me know.... My offer still stands for free CRC's to the top beta testers. Douglas Pippel has earned one hands down not only with the report of 2 of the 3 fixes, but also with previous recommendations... I think Doug deserves some 'atta-boy's thown his way. v1.37 notes: (time span from 1.36 - 37 days) CRC CHANGE! New one for 1.37! ----------- Docs, docs, docs... I know you do not like to read docs that much, but if you read ANY docs, read these. 1.37 is radically different than 1.36. If anything, it is more explanatory, certainly more configurable, and hopefully better. NEWS FLASH: Tracker now has a brain.. That's right, no more brain damage, no more keying in message bases, no more wondering if quotes are okay to use, no more speculating on whether or not you added in that new message base to TRAKMAIL.BBS.... never more! because there are many many new features. FIRST THING: Grab a piece of note paper and jot down the first 4 lines of TRAKMAIL.BBS so you know what to place in the new configuration file. Then, delete TRAKMAIL.BBS.. that's right, you never have to maintain another file!! Also, delete the ..\TRAKMAIL and ..\UTRAK directories that lie off of your GT directory and EVERYTHING in them. 'Cried the raven, nevermore!' --Poe (I think) NEXT: Run TRACKER /CONFIG and hold your breath. You'll probably get some beeps as Tracker wants to make sure you have your temporary directory set. Be sure that this temporary directory you set is one that DOES NOT exist already!! Tracker will create this directory, use it while it scans, clean up everything in it and delete it. It is VITALLY IMPORTANT that this is a fictional directory--one that only TRACKER will ever know about. I call mine "D:\TRAKJUNK\". THEN: You'll want to enter your BBS name and your CRC while at this main configuration menu along with ratios if you use them. Ratios ARE handled different in this release, but everything is explained for you on-screen NEXT: Push T for Text Configuration. You'll be sent to a new menu (one of a different color.. do you like it better?? Let me know.) Unless you are really compelled to change anything at this point, you're better off leaving these options alone until you have finished reading the docs. The power of Tracker v1.37ß lies in these configuration menus which allow you to totally control Tracker and what it does and can do! (IE: Everyone's Tracker can be totally different!) THEN: Hit [Esc] or [Q] to quit back to the main menu. Now push (C) for Color Configuration. This will allow you to totally configure Tracker's colors.... These color options allow for you to have up to 1820 different color combinations (of course, find a few you like and change them every so often). It's now going to be nice to be able to change to Red/White/Blue for the Fourth of July and Green/White for St. Patrick's day, etc... As you change the numbers on the top, the example at the bottom will change as well. NOW: Play around with the configuration a bit, but be sure to look at the powerful variables you can place in the (T)ext Configuration at the end of this document. Now, (Q)uit. You're changes will be saved into a TRACKER.CNF file. I am now going to outline changes to each part of Tracker. In your GTLOGON.BAT: No changes need to be made. One option that is still in the code, but does NOT work from remote is the /PAUSE option. This was to output a pause to the remote, but it doesn't want to accept keypresses from the remote. Therefore, it will not work from remote. In your GTLOGOFF.BAT: Again, no changes need to be made. Keep using the /END function! To SCAN all of your message bases: A major change has been made to Tracker's control files. Now, 2 files (TRACKER.CTL and TRACKER.NDX) control all of the message reporting. It has become interesting to note that people who had to physical drives (Seagate at least) were getting drive accesses on both drives, even though only 1 was being accessed by Tracker. Although I have not been able to trace the problem, I have cut down on the number of open files and how often I open and close the files that Tracker uses. Danny O'Day, a beta tester, is checking into this problem in greater detail. I have left a bit of debugging information (what I use while alpha testing) in the /SCAN routine to help with any problems that may crop up. The /SCAN function as a whole has slowed in some ways, but has speeded up in others. I hope that its a happy medium as this is probably the last hoorah for /SCAN. I have wrestled with it too long, and I think I've tackled it to my satisfaction this time. While loading in the user base, a 5 byte file will be created for each user on your system in the temporary directory you specified in /CONFIG. BE SURE YOU HAVE THE DRIVE SPACE as EACH file will take up the number of K that you've allocated to each cluster. On my drive it is 2K each, so for the 255 users I have, I need about 550k or so. These little files will only last for the duration of the SCAN and will be erased immediately afterwards! You will see the OPEN and CLOSED flags for each file as they are written. The words should flash by and not stay on OPEN for very long. Yes, you will notice a longer delay than before, but it will be made up for in the /SCAN. (I hope.) ** NEW FEATURE for /SCAN: While the /SCANQ feature is absent in 1.37, there is a new feature. /LOCAL:xxxxxx The /LOCAL: option may be used to designate certain access levels to only have the local message bases scanned. ** In order for Tracker to know which bases are local ones, the word 'local' must appear in any way, shape, form, or capitalization in the description of the message base in GTMDIR.BBS. If you run into problems with Tracker not picking up a base as being local, you may wish to try putting the word "local" in the first 74 characters of the base's description ** The 'xxxxx's after /LOCAL: represent the access levels to scan 'local message bases only' for. Just like the /EXEMPT: function in GTLOGON.BAT for Tracker and in GT itself, Level 'G' is different from 'g'. Example: TRACKER /SCAN /LOCAL:ABCDEFghij09 would mean that levels A, B, C, D, E, F, g, h, i, j, 0, and 9 would only get reports for local messages. This is quite useful for visiting GT sysops who read the echomail anyway. /SCAN in nightly maintanence. On my 12Mhz machine w/disk cache & 1 ST251-1 with a Perstor card, SCANning took 1.18 min to load 250 users and 3.45 to complete the SCANning of 1820 messages in 55 bases with no /LOCAL skips. Please evaluate it on your machine and report it in the echo. INIT: The /INIT function is still the same. Use it to periodically refresh the # of total calls. Remember that by using /INIT in the middle of the day that you destroy the 'calls today' counter. NULL: The /NULL option is quite useful for making absolutely sure that your WHOTODAY.?BS and WHOYEST.?BS files roll over at midnight (ex: in your nightly maint), and that the Sunday reports are done on a timely basis. Also, use TRACKER /NULL to simulate a call without adding to the calls for the day so that you can test new color configurations if necessary. OTHER NEW FEATURES AND HIGHLIGHTS --------------------------------- * The # of minutes left are now calculated and are correct at any given point. This allows for discrepancies in the time Tracker reported was left and the time GT said was left if the logon happened to be an unusually long one. * The /END function scans only bases that user had access to. This will speed up the unnecessary scanning of sysop message bases after a regular user logs off. Only the message bases he can access will be gleaned for new message bases. * The mail-waiting reporting has been enhanced to a great degree. Not only the message base that the message is waiting in appears, but also the base #, along with the sender and subject of the message. * When in local mode during logon, pauses will pop up so that you may read each screenful. * PENDING.CTL and TMAIL.CTL are 2 files that are present in the GT directory between logon and logoff. They are automatically erased along with YESMAIL.TRC and NOMAIL.TRC (depending on if the user had mail waiting--useful for those using STACKKEY to force users to read mail--a simple IF EXIST YESMAIL.TRC could be used to branch off to another batch file depending on your application of it) * Lots of other little bugs were corrected in this version. Two bugs still exist. One is with the /NO300, /NO1200, /NO2400, and /NO4800 switches not working sometimes. The other is with the remote /PAUSE function in logon that doesn't work from remote--only locally. These will be corrected in time--just wanted you to know. And finally, the power variables. The following variables can be substituted in the (T)ext configuration from the main menu of the TRACKER /CONFIG option. When using any of the variable substitutions, Tracker will automatically change from the current color to the HIGHLIGHT color, print the variable, and then change to the TEXT color. If you wish to keep a line red, for instance, you need to be sure to make it red at the first of the line, and immediately AFTER *EACH* variable you use. For a prime example, look at my "Ratio Caution line". Informational Variables Color Variables ----------------------- --------------- @F@ - first name of user @Y - yellow @L@ - last name of user @G - green @W@ - whole name of user @R - red @DK@ - number of kilobytes downloaded @H - highlight color (from config) @DF@ - number of files downloaded @I - general information color (config) @UK@ - number of kilobytes uploaded @X - text color (from config) @UF@ - number of files uploaded @LVL@ - access level of user @D@ - current date (always in the form, XX-XX-XX) @T@ - current time (always in the form, xX:XX ?m) (ex: 1:43 pm, 12:12 am, 8:30 pm) @B@ - current baud rate (DCE rate if using /OZ and WhoDis) @C@ - city of current user @P@ - unformatted phone number of current user @M@ - time left in minutes @LD@ - long date (ex: Saturday, December 23, 1989) @LO@ - full name of last user on @LC@ - city of last user on @CN@ - caller number of current caller @TC@ - total calls 'to date' to the BBS Lengthy eh? The best way to get a feel for these is to print out the (T)ext Configuration screen and run TRACKER /NULL and gaze at the screen to see and compare how the variables relate to the colors, etc. For example, to keep this line yellow with highlights on the variables, I need to do this: @YHello, this line is yellow - your name is @W@@Y - back to yellow! ^^ ^^^--- goes back to yellow. │ │ changes to yellow changes to highlight and BACK to text Again, you'll get the hang of it.. then again, you may just want to play around with the (C)olor Configuration and not mess with anything * Sysop Announcement feature. In (T)ext Configuration, the (S)ysop Announcement line is configurable. I use it to say something nice to the users like: @GMerry Christmas! to print a line of holiday cheer in green. Use your imagination! --- That's about all I can think of at this point. Please report in on how everything works out. Let me also take this chance to thank each and everyone of you for your time in testing Tracker. Have a very Merry Christmas and a great new decade... See you in the 90's, Cory v1.36 notes: ----------- As the beta test slows, I want to thank everyone who made a suggestion toward the further development of the program. I know you are glad that your suggestion made it in, and I want to thank everyone I can possibly thank off the top of my head: April Strong Douglas Pippel John Baird Raymond Wood Ken Kirkland Bryan Pike Edwin Smith Danny O'Day There are probably some others that I can't think of, and I apologize, but you know if you helped! Thanks! Now on with the 'long' awaited release of 1.36. CRC Required for Operation! This one is different from v1.35's CRC. Please find out what it is at the beta test site or on the home board. Features Disabled ----------------- /FULL is no longer an option with /REPORT. There will be 1 standard reporting function for now. ------------------------------------------------------------------------------ v1.39 BETA - NOT AUTHORIZED FOR RELEASE TO THE GENERAL PUBLIC Tracker v1.36ß - November 14, 1989 - Logon utility for GT15.XX ------------------------------------------------------------------------------ v1.36 BETA - NOT AUTHORIZED FOR RELEASE TO THE GENERAL PUBLIC ------------------------------------------------------------------------------ v1.36 notes: ----------- As the beta test slows, I want to thank everyone who made a suggestion toward the further development of the program. I know you are glad that your suggestion made it in, and I want to thank everyone I can possibly thank off the top of my head: April Strong Douglas Pippel John Baird Raymond Wood Ken Kirkland Bryan Pike Edwin Smith Danny O'Day There are probably some others that I can't think of, and I apologize, but you know if you helped! Thanks! Now on with the 'long' awaited release of 1.36. CRC Required for Operation! This one is different from v1.35's CRC. Please find out what it is at the beta test site or on the home board. Features Disabled ----------------- /FULL is no longer an option with /REPORT. There will be 1 standard reporting function for now. Enhanced Features ----------------- The WHOTODAY.* and WHOYEST.* bulletins have been refreshed with a new color and a more informative output. The actual output of the Tracker display has been revamped and recolored. I get quite sick of the same old thing, so I like to play switcheroo. The display is less choppy, not as bright and (I think) easier to read. This long-awaited reworking was originally suggested by April Strong. The /END function has also received a facelift along with a minor facelift of the /SCAN function. When /SCAN is run, your user base will be validated instead of rewritten. This should double the speed of the user loading if you were having problems with it. I recommend that you ERASE your UTRAK directory before you run /SCAN the first time with v1.36, and thereafter, Tracker should fly on its subsequent runs. /REPORT has been changed. Since the only option for reporting is /REPORT now, it has been condensed to a point, yet enhanced. April Strong suggested that the report show how many users are joined to a base. This way, you'll be able to see exactly how many people are in each base to see how popluar they are! New Features in v1.36ß ---------------------- /OZ is a feature that many of you with locked DTE will enjoy. With the /OZ function enabled, many will wish to stop using the /NOBAUD feature to provide users with a bit more information on the 1st line. Basically, /OZ will pick up the WHODIS.BBS file's DCE rate. I am not able to detect the actual carrier speed as WHODIS can. I urge you to pick up and register (free) WHODIS and run WHODIS /S /Q in the GTLOGON.BAT *BEFORE* running TRACKER with the /OZ function. Of course, you'll want to use WHODIS /U in your protocol batch files to show you who is downloading. /OZ will announce the actual DCE rate to the user. The previous "workaround" was the /NOBAUD function to keep Tracker from saying that the user had a 19200 baud connect, but some people still like /NOBAUD. Using /OZ with /NOBAUD together will have no effect and I do not recommend it. /SCANQ ------ In order to circumvent an apparent "problem" Tracker is having with people who have had VERY long scans, /SCANQ was suggested by Douglas Pippel. /SCANQ will pick up from either the last /SCAN or /SCANQ that you did. This will allow quick refreshes for those who run Netmail. Think of /SCANQ as being like /END, but to be used after netmail distribution. Do not use /SCANQ with /SCAN--they are 2 different options. As a result of this addition, you'll find 2 new files in TRACKER's directories: HIGHPTR.TRC and TRAKHIGH.PTR. Please don't mess with these. I am not sure how /REPORTing will work with /SCANQ; therefore, I recommend that you try to /SCAN once every day or so and keep your netmail runs up with /SCANQ. /NO300 /NO1200 /NO2400 ------- These new options may be used in any combination and in any order (as with all of the command line options). They will deny 300 baud, 1200 baud and 2400 baud callers respectively. You will need to have the file DROPDTRx.EXE (where x is the # of your COM port) in your GT directory for this option to work. DROPDTRx.EXE may also run as the first option in your GTLOGOFF.BAT to drop people off real fast so they don't have to wait for your GTLOGOFF.BAT file to run. All 4 of them are included. * Exemptions * If you wish to exempt certain 300 (or 1200, or 2400) baud callers and still run the /NOxxxx option, then you will need to make a file called ACCEPT.TRC in your GT directory. In this file, you will need to set it up like this: ACCEPT 300 John Wright Joe Wilks Jeffrey Treadaway END <- END mark ACCEPT.TRC can have up to 3 sections.. One with ACCEPT 300 to the END remark, one with ACCEPT 1200 to the END remark, and one with ACCEPT 2400 to the END mark. You need only make a section for each denial statment that you use. For example, if you use a /NO300 and /NO2400 *AND* you chose to exempt some users of each baud rate, then you'd have an ACCEPT 300 and ACCEPT 2400 section. This file is *TOTALLY OPTIONAL* and doesn't have to be used if you wish to flat-out deny a baud rate, but it is here for your convienience. By the way, you don't have to have a section for each /NOxxxx option you use. So, if I wanted to deny all 300 baud callers and only let a few of my 1200'ers in then my TRACKER command line would have /NO300 and /NO1200 in it, and then my ACCEPT.TRC file would look like this: ACCEPT 1200 My Friend END If a user is not of SYSOP level, then the following files will be created after the Tracker logon is completed: NOMAIL.TRC if the user has no mail waiting. YESMAIL.TRC if the user *HAS* mail waiting. This is a workaround to the problem with setting errorlevels, but it just as easy to use via batch files. Simply say: if exist NOMAIL.TRC STACKEY "N" (or whatever) if exist YESMAIL.TRC .... Again, these files will not be created if you are a sysop. The /END option will delete the YESMAIL/NOMAIL files when run in order to 'clean up' for the next caller. Concerns -------- I am quite concerned about the delay time with the /SCAN option. 10000 messages and 500 users should not take over 10 minutes on a 12 MHz machine. Please let me know the statistics on your BBS. That wraps it up for 1.36. I'd say that I have forgotten 1-2 minor minor details, but for the most part, I have covered it all. Now, do I have any offers to write the official docs? (GRIN) Cory ---- v1.35 notes: ----------- Hello again! This has probably been the longest delay between betas in awhile (grin..a whole 5 days). First off, let me thank EVERYONE again for helping me with suggestions and comments and most of all, encouragement. I will be posting a list of all the people who have helped me throughout the last month or so and they can treat themselves to a CRC for Tracker. (Yes, I said CRC).. Now, on with the details. Things removed: No more errorlevels are passed upon the termination of Tracker. I was having too many problems with it and therefore decided to remove that code. I hope to put it back in at a later date... someone remind me. New features ------------ CRC's. In beta form, Tracker must have a CRC code in order for the main code to work. There is a standard beta code that will function with the beta software until release. You can find the code on any of the support boards (TRC or April Strong's Boardwalk - PCPable via TXDAL). Therefore, a change will be introduced into the TRAKMAIL file. TRAKMAIL.BBS ------------ Simply add 2 new lines to the very top of the file. Line 1: Your BBS name Line 2: Your CRC Line 3: Mail waiting line... ... and it continues on in normal fashion. Options CHANGED on the command line: ----------------------------------- SCAN now becomes /SCAN END is now /END INIT is now /INIT /Q (quiet mode) is now /QUIET Please use these new formats since they WILL not work unless the '/' is in front of them. Be sure to change your batch files! NEW options on the command line: ------------------------------- /OVERRIDE is a new option when used with /INIT, will add the sysop's calls into the total count. This is not the same as the /OVERRIDE when used with the main screen. /REPORT ------- This one requires some explanation: TRACKER /SCAN /REPORT TRACKER /SCAN /REPORT /FULL These are the 2 possible combonations with the /REPORT and /FULL commands. As you can see, /REPORT will not work without /SCAN being present on the command line. Likewise /FULL will not take effect unless both /SCAN and /REPORT are on the command line. It matters not where you place any/all of these 3 parameters. If you do not wish a report (explanation below), then a simple /SCAN will do. Basically, the /REPORT option is run in tandem with the /SCAN option. After the completion of the /SCAN, a report is created. This report is placed in the sysop message base and contains a list of the number of messages on your BBS during this scan, the number you had last time and the difference between the 2. This is quite helpful to determine how many messages came in during netmail! It also will break down each message base that had new messages added or subtracted and report them with their totals. Using the /FULL option with the /SCAN option AND the /REPORT option will give you everything that the normal report gives you plus totals from EACH message base and verbose breakdowns of each message base. The totals won't be right the first time you run it, but they will be from then on out. It is imperative that you do not mess with the 2 new files created in your GT directory - TRAKSCAN.DAT and TRAKSCAN.OLD, the control files for this option. Pointers -------- If you go up and down multiple times per night for netmail and /SCAN after each one, that's fine. Be sure to only use the /REPORT option after your LAST netmail session to get the full count total. Remember that the /REPORT spans from the current scan back to the most recent time that you used the /REPORT option. Minor fixes ----------- -Apparently there was a misalignment problem in 1.34. It's fixed. -The first line ("Connected at.." or "It is presently...") will now be centered on the page. -Minor information display adjustments. -The /QUIET mode will display information on screen, so, if needed, can also be redirected to >>NUL if running under a multitasking environment. -All windowing code has been removed. -As stated before, the 'exit with errorlevel' feature has been disabled until further notice. I can't think of anything else, so that'll about wrap it up. Please enjoy and let me know if I can do anything else... even if it does sound like a wild idea. (That reporting option was one of my wild ideas...) Cory v1.34 notes: ----------- First off, I hope everyone had a Happy (and a safe) Halloween! Now down to business. -> While you are using this version, please watch for SHARE VIOLATION errors from DOS if you are using MMR and a large hard drive in which you have SHARE loaded (or a network). BTW, does anyone have the desire for NETWORK support? * New things: ------------ - Speeded up information retrieval. - Modified TRAK.BBS so that the user's access level would be printed on the last line - will not affect operation of existing GT+Plus Suite programs. * Added support for COM3: and COM4: plus operation from 38400-115200 baud. You can just use the /PORT: command and are now able to designate either 3 or 4. - Auto-detection of baud speed as set in UART chip. - Exits gracefully upon carrier loss; however, no errorlevel is set. Do you wish an errorlevel to be set if carrier is lost, or is that not too important? - New command line options: /XON - Use this if you use XON/XOFF handshaking /CTS - Use this if you need CTS hardware handshaking /BOTH - Enables both CTS and XON/XOFF handshaking (not sure which to use? Choose /BOTH) Note: Not necessary unless using a modem which requires flow control (such as 1200/2400 MNP or ANY 9600 baud modem). NO handshaking is the default. /OVERRIDE - This option will override the automatic 'SysOp Override'. Note that this option will treat the sysop as a normal user (ie: name is added to bulletin, increments the calls and shows the sysop's name as the last one on!); however, the 'detail' report on Sunday morning will still keep the sysop separate from the user counts. - The code was unfortunately enlarged by around 8K. This was a direct result of the new communications routines and was slightly influenced by some of the new code involving faster information retrieval. - Fixed a bug in the report on Sunday mornings where the sysop calls were being added incorrectly. - You'll notice a directory of 0 byte files named UTRAK off of your GT directory. This directory contains a list of your users (with names encoded in the Tracker format) since the last SCAN. This file is automatically maintained by Tracker and should not be tampered with. You probably should make a habit of trying to SCAN on a nightly basis to keep everything up to date. - Both the displays for the SCAN and for the END options have been enhanced to provide more information. You may notice that, while loading in the user base, you will see a "Reject" in red letters in the place of a name. This is due to the 'banned' or 'deleted' flag having been set in the USER.CTL file. - The main TRACKER window has been toned down and condensed to provide as much information in as little space as possible. In turn, I have been able to increase the size of the user output window. I still have not been able to resolve the speed at which the "mail waiting" flies by. I am considering an alternative in which a window would pop up and give you details on each piece of mail if you so desired (local mode only of course). What do you think? Place your comments in the beta echo please (I guess we'll see who's reading this..grin) - The END option has been given a dose of logic. It will not only report more information to you, but also will reject a new letter if the addressee is not in the user base (as determined by the control files in the UTRAK directory)-- hence the IMPORTANCE of a nightly scan. Boy... I didn't know I had done this much on this release! Enjoy! v1.33 notes: ----------- Fixed a bug where the message number would be overwritten by the description on the remote end. v1.32 notes: ----------- Out, out damn ZIP! (Pardon my French) Actually, poor Ken Kirkland (and others I'm sure) were getting massive delays. After talking with Ken, the ole' light bulb clicked on! Therefore, 1.32ß does things a new way. Once again, please SCAN before using this new version (you need not INIT again). SCAN loads both the message bases and the user base into memory then compares each message to your user base. This way, we can suppress creating data files for those users not on your system. SCAN is required whenever your message bases change massively (after ST or netmail -- see below), otherwise, END will suffice. New features: ------------ 1) /NULL is a new parameter that will cause a run of Tracker, but no calls will be added and no message bases will indexed (no TMAIL.CTL) I use it in my nightly event due to the fact that I had no way of knowing when I could copy over WHOYEST.BBS (since it is unpredictable when the first user of the day would log on), and I had to copy it in my already lengthy GTLOGOFF.BAT unnecessarily. (I know some probably rigged it up so that they copied a fake GTUSER.BBS file with their name and LOCAL baud over and then run Tracker, but now there's an official way to do it!) 2) This program will now be known as Tracker! instead of GT Tracker! 3) Tracker will exit with an errorlevel of 5 if there was an error in execution (such as user not found in the USER.CTL file, etc). ATTENTION: If you depend on Tracker for GT+Plus suite operation, extreme system problems may arise if you allow logon to continue (such as the current user taking the identity of the previous user in the doors, etc). Therefore, you should test for errorlevel 5 and if it comes out true, then tell the user that there is a problem and DROP DTR/HANG UP! Big errors like this should happen VERY rarely, but IF YOU DEPEND on the SUITE, you need to abort the logon! 4) The viewing window has been enlarged - Enjoy! ** Keep a watch on the call count. I have changed a few things, so keep your eye out for incorrect addition! v1.30 notes: ----------- If you haven't been keeping up with the betas, PLEASE read everything below this section. Major changes have occurred with each beta release, so you need to read from the bottom up, plus there have been quite a few changes in this beta also! 1) No structural file changes have occured, but you will need to SCAN due to the new way of handling the data files. PKZIP.EXE and PKUNZIP.EXE are required in a PATHed directory (it need not be in the same dir as Tracker). I am dubbing SCAN as 'Comprehensive Message Scanning' due to the quite lengthy scan time with each message base. I SCAN around 60 message bases (3000+ messages) in a little over 3 minutes at 12 MHz. SCAN needs only to be run when massive changes to the message base structure have occurred--this means after compressing ANY/ALL bases with Sysop Tools or after any mass mail has come in (netmail, echomail). The data files that TRACKER keeps contain information such as base number, message number, and actual record number (to enhance message lookup speed on the END scan), so you need to SCAN when massive changes have occurred. 2) The /NOBAUD option has been both fixed to line feed after it prints out to the user and has been reworded to make it sound nicer. You may wish to check out both with /NOBAUD and without /NOBAUD to see which one you like better. Also, anyone have an idea of what to call this option other than /NOBAUD 3) Mr. John Baird has recommended this nice addition: Tracker will now exit with an errorlevel depending on whether or not the user has mail waiting to facilitate the addition of something like STACKKEY after TRACKER has run. Tracker will exit with an errorlevel of 2 if the user has mail waiting and with errorlevel 0 when no mail is waiting for the user. Remember, just as in your batch file to bring up GT, that you check for errorlevels in descending order within the batch file. Does anyone have a recommendation as to what other results one would want an errorlevel for? 4) The /EXEMPT: option has been added by the request of Ed Bragg. Use /EXEMPT: on the command line to exempt users from getting the ratio message. Example: To exempt users with levels M,R,S,Q,a and 7, then use it like this: /EXEMPT:MRSQa7 Levels need not be in any particular order, and, of course, remember that level z is different than level Z. Tracker WILL NOT treat 'z' as 'Z' or vice versa! There is no limit to the number of access levels that can be exempted nor does it matter where you place the EXEMPT option on the command line, just as long as each option is delimited by a space (common sense). As of v1.30ß these are all the options that are available: TRACKER /PORT:1 /DELAY:3 /NOBAUD /EXEMPT:09IdQe Again, options can appear in any order as long as delimited by a space. Values shown above are not defaults, but just examples! 5) If /PORT: is not given, then it will default to 1. The only acceptable values for /PORT: are 1 and 2. 6) The reporting date has been moved to Sunday. 7) One more restriction: NO Quotes in your message description! Ex: D:\C,"C" Programming Echo would be unacceptable. 8) The SCAN option now shows how many messages it has scanned through. This is just some odd trivia that I thought I'd throw in for those interested in just how many messages there are on the BBS. 9) Any beta copy you receive will be in ZIP form and will have a comment in it that says something to the effect that it is an "Official Beta Release from The Rising Connection". Do not use anything other than official releases. If you run across a non-official release then let me know where you picked it up. That's about it. Anything I have forgotten (which I doubt) will be mentioned in the beta echo. All I can foresee going wrong is missing the mail. Watch for problems with your mail being/not being reported and let me know (netmail me at 070/002 or pop in the beta echo). Also, if your system begins to lock up and it hasn't been doing so before the use of v1.30ß of Tracker, PLEASE let me know. I have been using some new code and have experienced lockups, but have since changed code and do not expect problems, but I would like to keep tabs on it. Any lockups that would happen, will happen shortly after your GTLOGON.BAT runs (only applies after running the main option (/PORT:, /DELAY, etc)). I don't wish to make a big issue over it, but I just wanted you to be aware. As for estimating a release date, I think Nov.15 and by the latest, Thanksgiving, would be something that I can shoot for. Again, THANKS for beta testing. I appreciate your help! v1.29 notes: ----------- Things are moving fast here at TRC so thanks for keeping up! Do a SCAN before using this version (you need not run the INIT option) due to the change in the structure of the mail control files. Also, I have changed the TMAIL.CTL structure in the .\TRAKMAIL directory so that the message base scanning with END is sped up around another 5-10% from v1.28 and cuts down on the disk thrash. NEW COMMAND LINE! In order to fill some option requests, and to reduce the code a little bit, I have changed the command line. These options can appear ANYWHERE on the command line in ANY ORDER. /PORT:x where x is either 1 or 2 -- this designates the com port number and should be a single integer and NOT "COM1:" (Required parameter) /DELAY:x where x is the number of seconds to delay after execution of the program. I recommend running Tracker as the last thing in your GTLOGON.BAT file so that the user can see WHAT mail they have waiting and WHERE it is, but this option is included mainly for those who run DOORWAY (which clears the screen) after Tracker. x must be an integer from 1 to 9. For no delay, just don't use this parameter. (Optional Parameter) /NOBAUD this option will change the first line that Tracker displays to not show the baud rate. This was requested by April Strong because she locks her com port at 19200. Therefore, she can use this option to change the information that Tracker displays so that the 'Connected at 19200' won't show up to her callers (1200, 2400, etc. baud callers might be confused). Also, you can use the /NOBAUD option if you like it better than the standard one. (just trying to be flexible) CHANGES to the TRAKMAIL.BBS file: Right after line 2, you'll need to make 2 new lines: Line 1: line to print if mail is waiting for the user Line 2: " " no mail is waiting. Line 3: Ratio for FILES transferred Line 4: Ratio for KBytes transferred Lines 5 and beyond: Msg base path,Msg Base description Again, be sure you have no blank lines at the end of this file. Now, to explain the Ratio concept as implemented in GT Tracker: Simply put, Line 3 shows the minimum ratio of files uploaded to files downloaded that you wish your users to have. Line 4 is the same, but applies for KB. If EITHER ratio is found to have been exceeded by the user, it will say "Caution: You have downloaded xK in x files, but only uploaded yK in y files." It will not log the user off or yell at them, but will give a friendly, indirect reminder about their upload/download habits. If you do not wish to use this feature, place a 0 on Lines 3 and 4. It is possible to use just the file ratio or just the KB ratio by placing a 0 in the one you don't want to use. Be sure you have SOME kind of value on both lines 3 and 4 because Tracker doesn't expect message base paths until line 5. You may ask--what numbers do I place on lines 3 and 4? I can better answer this with an example: If you want the user to be warned if they exceed 1 upload to 5 downloads, then you'd say 1 / 5 which would equal .200, 30K uploaded for every 100K downloaded would be 30 / 100 = .300 Take a look at my TRAKMAIL.BBS file for what I have. In conclusion the formula is "UPLOAD / DOWNLOAD" What you need to look for: Try to hit the pause button to see if all of your mail that Tracker reports is all of the mail you have. Douglas Pippel has occasionally had more mail than Tracker reported and can't seem to find a pattern to it. Please keep a close watch on what happens... Also, let me remind you that you should SCAN with Tracker when you compress your file bases or after each/every netmail session. Regards, Cory v1.28 notes: ----------- New things! First off, a word of warning-BE SURE *NOT* to have extra semicolons and commas in your descriptions. ALSO, DO NOT put extra lines into the TRAKMAIL.BBS file. Next, a new code has been added. In the first 2 lines of TRAKMAIL.BBS where you enter the line for mail waiting and no mail waiting, you may use a variable named @FIRST@. An example may work better: "@FIRST@, you have these pieces of mail waiting:" where the @FIRST@ would be translated into the user's first name. My TRAKMAIL.BBS file (included in ZIP) shows examples. Be sure that you don't use the code more than once in the line! I forgot the code to trap errors... it's now fixed. WHOYEST.?BS (yesterday's caller log) now shows a total of callers at the end. Fixed a problem with too many linefeeds on the remote end between the message reporting and the final line. If anyone has suggestions on other "@CODE@" codes, please let me know! Remember to watch for the TRACKER.ERR file and also to be careful about how you format the descriptions in TRAKMAIL.BBS. The SCAN option now shows message numbers and "loading in message tables". If you DO have any problems with the SCAN option and your TRAKMAIL.BBS file, please watch the tables load (green and white color...you'll see) and trace your problem... Regards, Cory v1.25 notes: ----------- I have included my TRAKMAIL.BBS file for your reference due to my change of logic. With this version, the rescan in the GTLOGOFF.BAT file has been GREATLY enhanced, therefore I am now scanning all 40-some-odd echos I have with very little delay. You may also wish to change line 1 of TRAKMAIL.BBS to look like mine: You have the following pieces of mail waiting: because Tracker now gives a listing of the specific message number and area name that their mail is waiting in. You may leave the "no mail waiting" line as is. Again, BE SURE not to have any extra commas or semicolons in the description of your area after the path names in TRAKMAIL.BBS because (as noted below) you will be asking for problems. I am still wrestling with some quirks with netmail, but I think I have pretty much got everything down-pat. I encourage you to scan ALL of your echo areas and let me know how it goes. Also, a TRACKER INIT and TRACKER SCAN will be in order before you begin full use of this version. I have corrected a bug where Tracker would write callers who did not complete the logon sequence to the bulletin. The file WHOYEST.BBS and WHOYEST.CBS will be created in addition to the standard WHOTODAY.BBS and WHOTODAY.CBS. Of course, the WHOYEST files show who was on yesterday and the WHOTODAY files show who has been on so far today. You may notice that when you log on, Tracker will fly right by... well, this is a user logon utility (GRIN).... Use the pause feature (TRACKER X Y where Y is the delay from 1-9 seconds) to slow it down if you wish. Also, if you lock DTE, Tracker will report to all callers what your fixed DTE speed is. I don't consider this any big deal, but I'd thought I'd let you know. I have coded in a little surprise for Monday mornings. When you wake up and read your mail, you'll find a little summary of last week's operations in your message base. It will be a little off the first partial week you use it, but once you have completed a full week, I think you'll find this feature one you can't live without and the results quite interesting and informative. I hope everyone will install this on their systems so we can run for at least a full week and see how it goes. I expect to release this around Nov. 10 or before if all goes well. Please report in to me with all problems you find. Regards, Cory -------------------------------------------------------------------------- v1.20 notes: ----------- > Friday the 13th - Let's hope my luck is good... it has been good all day > today, so let's hope this goes well. ** IT WASN'T.. Well, v1.25 should fix it. One thing to note: Please DO ** NOT use ANY commas or semicolons in your message base descriptions. If you do, you are asking for problems. Things to look for as a beta tester: First of all, note the TRAKMAIL.BBS file changes down below!!! Next, be on the lookout for incorrect message #'s in the logon (you'll know what I mean) Also, I have been having problems with netmail areas. I have fixed GT Tracker so that it doesn't pick up your outgoing netmail, but, in the process, I botched it so that it won't pick up incoming Netmail. I think that's about the only bug I have found, but keep your eyes peeled for the dreaded TRACKER.ERR file and FA it to me at 070/002 if you find it. Finally, let me reiterate that you DO NOT skip the execution of GT Tracker when logging on locally. DO NOT DO THIS. GT Tracker picks up the fact that you are a sysop and bypasses adding a call to the count (if you have level 0 as you should!). Please DO NOT SKIP it when logging on. BE SURE IT IS RUN BOTH IN THE LOGON AND LOGOFF BATCH FILE *EVERY TIME* someone logs onto the BBS. Otherwise, it WILL fail to function properly!!!!!!!! (Yes I am yelling) ------------------------------------------------------------------------------ This is a logon utility for GT Power, and while I cannot write complete documentation for beta programs, I will do my best to get you going. First make a TRAKMAIL.BBS file in your GT directory that is a listing of the path names to the message areas you wish to scan (Ex: D:\MAINMSG) [a trailing backslash is not required and each area must be on a separate line] **> Please do not scan ALL of your echomail areas (in the interest of time). A simple scan of just your local message bases will inform users who do not read mail on a regular basis of mail actually waiting for them. Any echomail fan will automatically choose YES for scanning mail. Trust me (and my beta testers) that only a few scanned message bases is the best method!! NEW FEATURES IN v1.25 beta -- For those wanting to benefit by the new Super Index feature of the other GT+Plus Suite programs, but do not want to output anything to the user, you may suppress everything by using a /Q on the command line. EX: TRACKER /Q -- When you use this option, you need not run TRACKER END or anything. Simply running TRACKER INIT once to create the TRAK.BBS file will suffice. From then on out, TRACKER /Q will be silent when run, yet will allow you to unlock the Super Index of v1.50 of The GTGap and v1.25 of GTAccess. IMPORTANT!!!!! -------------- *** v1.25 has a new format for the TRAKMAIL.BBS file-- Line 1: The line to print if the user has mail waiting Line 2: The line to print if the user does NOT have mail waiting For all subsequent lines, list the directories you wish to scan for mail as they are printed in your GTMDIR.BBS file. Not all need to be included. For instance, I just scan local and netmail (2 areas total) and say on line 2: "You have no LOCAL mail, but echo areas are NOT scanned." It is up to you. v1.25 also will not lock up when you scan many message bases. My TRAKMAIL.BBS file is included, but be sure to list your message bases in this fashion (NEW for 1.25ß): SAMPLE TRAKMAIL.BBS file ------------------------ Line 1: You have mail waiting locally; please choose YES to read it. Line 2: You have no LOCAL mail; however, ECHO areas are NOT scanned. Line 3 and beyond: D:\MAINMSG,General Messages Area D:\NET,Netmail Area Of course, you need to scan at least 1 message area, and up to 150 max. Also, do not have any commas or semicolons in your descriptions! Not Acceptable: D:\ECHO1,Local Sysop Echo (fun,fun!) <-ILLEGAL! -------------------------------------------------------------------------- To initialize Tracker run: TRACKER INIT <- I recommend not using this nightly, but DEFINITELY the first time you run TRACKER, and then only when you have deleted tons of users, etc. then TRACKER SCAN <- do this nightly, if not after each echomail session Make the following modifications to your batch files: GTLOGON.BAT: ------------ Tracker X Y <- where X is the com port number, and Y is the delay if desire to have one (after execution) [Y may not be greater than 9 or less than 1] ** If you do not wish to have a pause after running Tracker, do NOT enter a value for Y - TRACKER X will suffice. ** Tracker is self sufficient. Do not redirect the output or anything else. Tracker is TRANSPARENT to all sysop activity (except for messages left), therefore DO NOT skip over it in logon. GTLOGOFF.BAT: ------------- Tracker END <- Please run this anywhere in the LOGOFF batch file. ALL OF THESE STEPS ARE CRITICALLY IMPORTANT If you run into any errors, which is entirely possible with Beta software, please look at the TRACKER.ERR file created in your GT directory. If at all possible please FILE ATTACH them to me (as they will be quite small) along with writing a message to me describing the circumstances. You may use TRACKER /Q to silence all output (even to the COM port) to enable the use of the GT+Plus Super Index feature in The GTGap and GTAccess.